Added option to force usage of router file #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
if (file_exists($filePath) && is_file($filePath)) {
return false; // serve the requested resource as-is.
} elseif ($userRouter) {
return $userRouter;
}the reason why router is not used is because the requested resource is exists |
|
Yes, I understand that is why the router is only used for some requests. My issue is that I need all requests to go to the router, even if the resource exists in the document root directory. |
tiger-seo
force-pushed
the
master
branch
3 times, most recently
from
794932d to
e0509bb
Compare
tiger-seo
force-pushed
the
master
branch
3 times, most recently
from
ae1ad2e to
a79b3e4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Problem
I needed to be able to have all server requests to the php built in server utilize my custom router.php file. This extension has a built in router which sometimes sends requests straight to the servers document root and sometimes sends requests to the specified router.php file.
The Fix
I added an option to allow the developer to configure this extension to always send requests to the specified router file, regardless of the contents of document root.
Works like this: